Description

Roles

Attributes

Steps

1. Refine project plan:

   Depending on the results of the previous iteration assessment the Project Manager may need torevise the Project Plan. Necessary changes can encompass the need to acquire new resources, toabsorb an unplanned effort increase, or to implement a specific change request. If a change affects defined projectmilestones, the Project Manager should consult with the stakeholders before committing to them.

2. Define the iteration objectives:

   Work with the team to refine the iteration objectives found in the Project Plan, and document them in the Iteration Plan in order to provide high-level direction to what should be targeted for the iteration. The objectives should be driven based on Stakeholder priorities, and will be revised as the iteration plan is finalized. Those objectives are usually defined as high-level capabilities or scenarios that need to be implemented and tested during the iteration in order to deliver increased value to the customer.

3. Commit work to the iteration:

   The Project Manager works with the rest of the team, and especially the project stakeholders, to identify the high-priority work items from the Work Items List to be addressed. The high-level objectives provide guidance on what work items should be considered. The Iteration Plan from previous iteration should include an assessment of the results and can also be used as input to the current iteration planning. The team reviews its velocity and determines the amount of work that can be done within the iteration. The team breaks down into tasks those work items that are assigned to the iteration and estimates the effort to complete each task. Typical tasks range from half day to two days in lenght.

    

   When a team has decided to take on a work item, it will assign the work to one or several team members. Ideally, this is done by team members signing up to do the work, since this makes people motivated and committed to doing the job, but based on culture, you may instead have the project manager assign the work.

4. Review risks:

   Throughout the project, new assumptions and concerns may arise. The team identifies and prioritizes new risks as part of iteration planning, updating the Risk List. Responses to risks are added to the Work Items List, influencing the work that is being planned for that iteration.

5. Define evaluation criteria:

   Each iteration should include testing as a part of the evaluation, and the test objectives and test cases that need to be detailed. Other evaluation criteria may include successful demonstrations to key stakeholders, or favorable usage by a small group of target users. Document evaluation criteria in the Iteration Plan.

Inputs and Outputs

WorkProduct	Input	Output	Allowable States
Architecture Notebook			(none)
Iteration Plan			(none)
Project Plan			(none)
Risk List			(none)
Vision			(none)
Work Items List			(none)

Other Instances

Instance Parent
Enterprise OpenUP (with CobiT)Inception Iteration [1..n]Plan and Manage Iteration (Inception Iteration [1..n])
Enterprise OpenUP (with CobiT)Construction Iteration [1..n]Plan and Manage Iteration (Construction Iteration [1..n])
Enterprise OpenUP (with CobiT)Transition Iteration [1..n]Plan and Manage Iteration (Transition Iteration [1..n])